Standardized format for reporting error events occurring within logically partitioned multiprocessing systems

ABSTRACT

A method, system, and product in a computer system are described for reporting error events which occur within the computer system. The computer system includes multiple logical partitions. Each of the logical partitions includes a different one of multiple, different operating systems. A format is specified for reporting error events. An error event occurring within one of the logical partitions is detected. Information about the error event is formatted according to the specified format. Each operating system utilizes this format to report error events.

BACKGROUND OF THE INVENTION

[0001] 1. Technical Field

[0002] The present invention relates generally to data processingsystems, and more particularly to logically partitioned multiprocessingsystems. Still more particularly, the present invention relates to astandardized format for reporting error events which occur withinmultiple, different operating systems included within a logicallypartitioned multiprocessing system.

[0003] 2. Description of Related Art

[0004] Logical partitioning is the ability to make a singlemultiprocessing system run as if it were two or more independentsystems. Each logical partition represents a division of resources inthe system and operates as an independent logical system. Each partitionis logical because the division of resources may be physical or virtual.An example of logical partitions is the partitioning of a multiprocessorcomputer system into multiple independent servers, each with its ownprocessors, main storage, and I/O devices. One of multiple differentoperating systems, such as AIX, LINUX, or others, can be running in eachpartition.

[0005] In a Logically Partitioned (LPAR) multiprocessing system, thereare a class of errors (Local) that are only reported to the assigned orowning partition's operating system. Failures of I/O adapters which areonly assigned to a single partition's operating system are an example ofthis. There is also another class of errors (Global) that are reportedto each partition's operating system because they could potentiallyaffect each partition's operation. Examples of this type are powersupply, fan, memory, and processor failures.

[0006] When a serviceable event occurs within one of the logicalpartitions or is reported to the operating system in the partition, theoperating system being executed by that logical partition will execute adiagnostic routine to gather information about the event.

[0007] Each operating system will likely have different diagnosticcapabilities and different formats for reporting error events. Insystems having logical partitioning, and thus which support differentoperating systems, error events will be reported in a variety ofdifferent formats. This can cause a problem for a service techniciancalled to repair the error by creating confusion for the servicetechnician.

[0008] Therefore, a need exists for a method, system, and product forproviding a standardized format for reporting error events by any ofmultiple, different operating systems capable of being executed by alogically partitioned multiprocessing system.

SUMMARY OF THE INVENTION

[0009] A method, system, and product in a computer system are describedfor reporting error events which occur within the computer system. Thecomputer system includes multiple logical partitions. Each of thelogical partitions may include a different one of multiple, differentoperating systems. A format is specified for reporting error events. Anerror event occurring within one of the logical partitions is detected.Information about the error event is formatted according to thespecified format. Each operating system utilizes this format to reporterror events.

[0010] The above as well as additional objectives, features, andadvantages of the present invention will become apparent in thefollowing detailed written description.

BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The novel features believed characteristic of the invention areset forth in the appended claims. The invention itself, however, as wellas a preferred mode of use, further objectives and advantages thereof,will best be understood by reference to the following detaileddescription of an illustrative embodiment when read in conjunction withthe accompanying drawings, wherein:

[0012]FIG. 1 depicts a pictorial representation of a distributed dataprocessing system in which the present invention may be implemented;

[0013]FIG. 2 depicts a block diagram of a data processing system inwhich the present invention may be implemented;

[0014]FIG. 3 depicts a block diagram of an exemplary logicallypartitioned platform in which the present invention may be implemented;

[0015]FIG. 4 is a block diagram of the logically partitionedmultiprocessing server computer system of FIGS. 1 and 2 and a hardwaresystem console in accordance with the present invention;

[0016]FIG. 5 is a block diagram which illustrates a standardized formatwhich may be used by different operating systems to report error eventsaccording to the present invention; and

[0017]FIG. 6 is a high level flow chart which depicts differentoperating systems reporting error event information in a standardizedformat in accordance with the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0018] A preferred embodiment of the present invention and itsadvantages are better understood by referring to the (figures, likenumerals being used for like and corresponding parts of the accompanyingfigures.

[0019] The invention is preferably realized using a well-known computingplatform, such as an IBM RS/6000 server running the IBM AIX operatingsystem. However, it may be realized in other popular computer systemplatforms, such as an IBM personal computer running the MicrosoftWindows operating system or a Sun Microsystems workstation runningoperating systems such as UNIX or LINUX, without departing from thespirit and scope of the invention.

[0020] The present invention is a method, system, and product whichprovide for a standardized format for reporting error events which occurwithin the computer system. The computer system includes multiplelogical partitions. Each of the logical partitions may include adifferent one of multiple, different operating systems.

[0021] The standardized format is used by each of these differentoperating systems for reporting error events. In this manner, the sametype of data will be reported in a consistent manner by each differentoperating system.

[0022] An error event log entry will be created by an operating systemfor each error event. Each error event log entry can include anidentification of the operating system which is reporting the error, adiagnostic format, a diagnostic mode, an error code, a sequence number,an error time-stamp, descriptive text, location codes, field replaceableunit part numbers, a partition identifier, a machine type, a resourcename, a host name, a date and time, a serviced flag, and operatingsystem specific information. This information collected for each errorevent is described below in more detail.

[0023] With reference now to the figures, and in particular withreference to FIG. 1, a pictorial representation of a distributed dataprocessing system is depicted in which the present invention may beimplemented.

[0024] Distributed data processing system 100 is a network of computersin which the present invention may be implemented. Distributed dataprocessing system 100 contains network 102, which is the medium used toprovide communications links between various devices and computersconnected within distributed data processing system 100. Network 102 mayinclude permanent connections, such as wire or fiber optic cables, ortemporary connections made through telephone connections.

[0025] In the depicted example, server 104 is connected to hardwaresystem console 150. Server 104 is also connected to network 102, alongwith storage unit 106. In addition, clients 108, 110 and 112 are alsoconnected to network 102. These clients, 108, 110 and 112, may be, forexample, personal computers or network computers. For purposes of thisapplication, a network computer is any computer coupled to a networkthat receives a program or other application from another computercoupled to the network. In the depicted example, server 104 is alogically partitioned platform and provides data, such as boot files,operating system images and applications, to clients 108-112. Hardwaresystem console 150 may be a laptop computer and is used to displaymessages to an operator from each operating system image running onserver 104, as well as to send input information received from theoperator, to server 104. Clients 108, 110 and 112 are clients to server104. Distributed data processing system 100 may include additionalservers, clients, and other devices not shown. Distributed dataprocessing system 100 also includes printers 114, 116 and 118. A client,such as client 110, may print directly to printer 114. Clients, such asclient 108 and client 112, do not have directly attached printers. Theseclients may print to printer 116, which is attached to server 104, or toprinter 118, which is a network printer that does not require connectionto a computer for printing documents. Client 110, alternatively, mayprint to printer 116 or printer 118, depending on the printer type andthe document requirements.

[0026] In the depicted example, distributed data processing system 100is the Internet, with network 102 representing a worldwide collection ofnetworks and gateways that use the TCP/IP suite of protocols tocommunicate with one another. At the heart of the Internet is a backboneof high-speed data communication lines between major nodes or hostcomputers consisting of thousands of commercial, government, education,and other computer systems that route data and messages. Of course,distributed data processing system 100 also may be implemented as anumber of different types of networks such as, for example, an intranetor a local area network.

[0027]FIG. 1 is intended as an example and not as an architecturallimitation for the processes of the present invention.

[0028] With reference now to FIG. 2, a block diagram of a dataprocessing system, which may be implemented as a logically partitionedserver, such as server 104 in FIG. 1, and in which the present inventionmay be implemented is depicted. Data processing system 200 may be asymmetric multiprocessor (SMP) system including a plurality ofprocessors 201, 202, 203, and 204 connected to system bus 206. Forexample, data processing system 200 may be an IBM RS/6000, a product ofInternational Business Machines Corporation in Armonk, N.Y., implementedas a server within a network. Alternatively, a single processor systemmay be employed. Also connected to system bus 206 is memorycontroller/cache 208, which provides an interface to a plurality oflocal memories 260-263. I/O bus bridge 210 is connected to system bus206 and provides an interface to I/O bus 212. Memory controller/cache208 and I/O bus bridge 210 may be integrated as depicted.

[0029] Data processing system 200 is a logically partitioned dataprocessing system. Thus, data processing system 200 may have multipleheterogeneous operating systems (or multiple instances of a singleoperating system) running simultaneously. Each of these multipleoperating systems may have any number of software programs executingwithin in it. Data processing system 200 is logically partitioned suchthat different I/O adapters 220-221, 228-229, 236, and 248-249 may beassigned to different logical partitions.

[0030] Thus, for example, suppose data processing system 200 is dividedinto three logical partitions, P1, P2, and P3. Each of I/O adapters220-221, 228-229, 236 and 248-249, each of processors 201-204, and eachof local memories 260-263 is assigned to one of the three partitions.For example, processor 201, memory 260, and I/O adapters 220, 228, and229 may be assigned to logical partition P1; processors 202-203, memory261, and I/O adapters 221 and 236 may be assigned to partition P2; andprocessor 204, memories 262-263, and I/O adapters 248-249 may beassigned to logical partition P3.

[0031] Each operating system executing within data processing system 200is assigned to a different logical partition. Thus, each operatingsystem executing within data processing system 200 may access only thoseI/O units that are within its logical partition. Thus, for example, oneinstance of the Advanced Interactive Executive (AIX) operating systemmay be executing within partition P1, a second instance (image) of theAIX operating system may be executing within partition P2, and a Windows2000 operating system may be operating within logical partition P3.Windows 2000 is a product and trademark of Microsoft Corporation ofRedmond, Wash.

[0032] Peripheral component interconnect (PCI) Host bridge 214 connectedto I/O bus 212 provides an interface to PCI local bus 215. A number ofInput/Output adapters 220-221 may be connected to PCI bus 215. TypicalPCI bus implementations will support between four and eight I/O adapters(i.e. expansion slots for add-in connectors). Each I/O Adapter 220-221provides an interface between data processing system 200 andinput/output devices such as, for example, other network computers,which are clients to data processing system 200.

[0033] An additional PCI host bridge 222 provide an interface for anadditional PCI bus 223. PCI bus 223 is connected to a plurality of PCII/O adapters 228-229 by a PCI bus 226-227. Thus, additional I/O devices,such as, for example, modems or network adapters may be supportedthrough each of PCI I/O adapters 228-229. In this manner, dataprocessing system 200 allows connections to multiple network computers.

[0034] A memory mapped graphics adapter 248 may be connected to I/O bus212 through PCI Host Bridge 240 and EADS 242 via PCI buses 241 and 244as depicted. Also, a hard disk 250 may also be connected to I/O bus 212through PCI Host Bridge 240 and EADS 242 via PCI buses 241 and 245 asdepicted.

[0035] A PCI host bridge 230 provides an interface for a PCI bus 231 toconnect to I/O bus 212. PCI bus 231 connects PCI host bridge 230 to theservice processor mailbox interface and ISA bus access passthrough logic294 and EADS 232. The ISA bus access passthrough logic 294 forwards PCIaccesses destined to the PCI/ISA bridge 293. The NV-RAM storage isconnected to the ISA bus 296. The Service processor 235 is coupled tothe service processor mailbox interface 294 through its local PCI bus295. Service processors 235 is also connected to processors 201-204 viaa plurality of JTAG/I²C buses 234. JTAG/I²C buses 234 are a combinationof JTAG/scan busses (see IEEE 1149.1) and Phillips I²C busses. However,alternatively, JTAG/I²C buses 234 may be replaced by only Phillips I²Cbusses or only JTAG/scan busses. All SP-ATTN signals of the hostprocessors 201, 202, 203, and 204 are connected together to an interruptinput signal of the service processor. The service processor 235 has itsown local memory 291, and has access to the hardware op-panel 290.

[0036] When data processing system 200 is initially powered up, serviceprocessor 235 uses the JTAG/scan buses 234 to interrogate the system(Host) processors 201-204, memory controller 208, and I/O bridge 210. Atcompletion of this step, service processor 235 has an inventory andtopology understanding of data processing system 200. Service processor235 also executes Built-In-Self-Tests (BISTs), Basic Assurance Tests(BATs), and memory tests on all elements found by interrogating thesystem processors 201-204, memory controller 208, and I/O bridge 210.Any error information for failures detected during the BISTs, BATs, andmemory tests are gathered and reported by service processor 235.

[0037] If a meaningful/valid configuration of system resources is stillpossible after taking out the elements found to be faulty during theBISTs, BATs, and memory tests, then data processing system 200 isallowed to proceed to load executable code into local (Host) memories260-263. Service processor 235 then releases the Host processors 201-204for execution of the code loaded into Host memory 260-263. While theHost processors 201-204 are executing code from respective operatingsystems within the data processing system 200, service processor 235enters a mode of monitoring and reporting errors. The type of itemsmonitored by service processor include, for example, the cooling fanspeed and operation, thermal sensors, power supply regulators, andrecoverable and non-recoverable errors reported by processors 201-204,memories 260-263, and bus-bridge controller 210.

[0038] Service processor 235 is responsible for saving and reportingerror information related to all the monitored items in data processingsystem 200. Service processor 235 also takes action based on the type oferrors and defined thresholds. For example, service processor 235 maytake note of excessive recoverable errors on a processor's cache memoryand decide that this is predictive of a hard failure. Based on thisdetermination, service processor 235 may mark that resource fordeconfiguration during the current running session and future InitialProgram Loads (IPLs). IPLs are also sometimes referred to as a “boot” or“bootstrap”.

[0039] Those of ordinary skill in the art will appreciate that thehardware depicted in FIG. 2 may vary. For example, other peripheraldevices, such as optical disk drives and the like, also may be used inaddition to or in place of the hardware depicted. The depicted exampleis not meant to imply architectural limitations with respect to thepresent invention.

[0040] With reference now to FIG. 3, a block diagram of an exemplarylogically partitioned platform is depicted in which the presentinvention may be implemented. The hardware in logically partitionedplatform 300 may be implemented as, for example, server 200 in FIG. 2.Logically partitioned platform 300 includes partitioned hardware 330,Open Firmware 310, and operating systems 302-308. Operating systems302-308 may be multiple copies of a single operating system or multipleheterogeneous operating systems simultaneously run on platform 300.

[0041] Partitioned hardware 330 includes a plurality of processors332-338, a plurality of system memory units 340-346, a plurality ofinput/output (I/O) adapters 348-362, and a storage unit 370. Each of theprocessors 342-348, memory units 340-346, and I/O adapters 348-362 maybe assigned to one of multiple partitions within logically partitionedplatform 300, each of which corresponds to one of operating systems302-308. NV-RAM is divided between each of the partitions; it is notassigned to any one specific partition.

[0042] Open Firmware 310 performs a number of functions and services foroperating system images 302-308 to create and enforce the partitioningof logically partitioned platform 300. Firmware is “software” stored ina memory chip that holds its content without electrical power, such as,for example, read-only memory (ROM), programmable ROM (PROM), erasableprogrammable ROM (EPROM), electrically erasable programmable ROM(EEPROM), and non-volatile random access memory (non-volatile RAM).

[0043] Open Firmware 310 provides the OS images 302-308 running inmultiple logical partitions each a virtual copy of a console andoperator panel. The interface to the console is changed from anasynchronous teletype port device driver, as in the prior art, to a setof Open Firmware calls that emulate a port device driver. The OpenFirmware 310 encapsulates the data from the various OS images onto amessage stream that is transferred to a computer 380, known as ahardware system console.

[0044] Open Firmware 310 includes system boot firmware. A mechanismbuilt into each of processors 332-338 as an architected instructionallows system firmware 310 to execute at any time. Thus, systemcheckpoints may be immediately displayed to the operator panel window onhardware system console 380 and also immediately logged to non-volatilerandom access memory (NV-RAM) even before the I/O path to these deviceshas been configured to accept any programmed input/output (PIO)accesses.

[0045] Hardware system console 380 is connected directly to logicallypartitioned platform 300 as illustrated in FIG. 3, or may be connectedto logically partitioned platform through a network, such as, forexample, network 102 in FIG. 1. Hardware system console 380 may be, forexample, a desktop or laptop computer. Hardware system console 380decodes the message stream and displays the information from the variousOS images 302-308 in separate windows, at least one per OS image.Similarly, keyboard input information from the operator is packaged bythe hardware system console, sent to logically partitioned platform 300where it is decoded and delivered to the appropriate OS image via theOpen Firmware 310 emulated port device driver associated with the thenactive window on the hardware system console 380.

[0046]FIG. 4 is a block diagram of the logically partitionedmultiprocessing server computer system of FIGS. 1 and 2 and a hardwaresystem console in accordance with the present invention.

[0047] Server 104 includes a plurality of operating system (OS)partitions 402, 404, 406, and 408. These partitions receive inputs frominput/output (I/O) devices, and from base hardware, which may be a powersupply, a cooling supply, a fan, memory, and processors. Any one ofmultiple, different operating systems, such as AIX or LINUX, can berunning in any partition. For example, AIX is shown in partitions 402and 406, while LINUX is shown in partitions 404 and 408. Although fouroperating system partitions are shown, any number of partitions with anyone of a variety of different operating systems may be utilized.

[0048] Each partition includes an error log and a manager. When an erroroccurs within a partition, the error is logged into the partition'serror log. The manager formats error information into the standardformat and forwards the error information in the form of an error eventlog entry to hardware system console 380. For example, partition 402includes error log 410 and manager 412; partition 404 includes error log414 and manager 416; partition 406 includes error log 418 and manager420; and partition 408 includes error log 422 and manager 424.

[0049]FIG. 5 is a block diagram which illustrates a standardized format500 which may be used by different operating systems to report errorevents according to the present invention. Format 500 includes aplurality of fields 502-532. Field 502 is an operating system identifierfield for identifying which operating system is being executed by thelogical partition and reporting the error. Field 504 is a diagnosticformat field for identifying the type of diagnostic routine executed bythe operating system. Field 506 is a diagnostic mode field indicateswhether the operating system was up and running customer applicationswhen the error occurred by indicating “concurrent”, or whether it wasunavailable for users at the time by indicating “service”. Field 508 isan error code field which indicates the particular error code determinedwhen the operating system executed the diagnostic routine. The errorcode identifies the failing field replaceable unit (FRU). Field 510 is asequence number field for indicating whether the error information wasobtained from an error log. Field 512 is an error time-stamp field whichindicates the time and date the error occurred. Field 514 is adescriptive text field for storing a textual description. Field 516 is alocation codes field for indicating the physical location of the failingFRU. Field 518 is a field replaceable unit part number field for storingthe part numbers and/or serial numbers of the particular unit within thecomputer system which should be replaced. Field 520 is a partitionidentifier and name field for identifying the partition. Field 522 is amachinetype/Model/serial number field for storing the machine type andmodel and/or serial number of the computer system which includes thepartition which generated the error event. Field 524 is a resource namefield for indicating the resource name used to identify the failingdevice. Examples of resource names includes “fan0”, “processor2”, andother common names. Field 526 is a host name field for identifying thehost name of the computer system. Field 528 is a date and time fieldwhich indicates the time and date the error was logged within thecomputer system. Field 530 is a serviced flag field for identifyingwhether this error event has been serviced. And, field 532 is anoperating system specific information field for storing any additionaloperating system specific information.

[0050]FIG. 6 is a high level flow chart which depicts differentoperating systems reporting error event information in a standardizedformat in accordance with the present invention. The process starts asillustrated by block 600 and thereafter passes to block 602 whichdepicts an error event occurring within one of the logical partitions.Next, block 604 illustrates the operating system which is being executedfrom the logical partition detecting or being notified about the errorevent. Thereafter, block 606 depicts the operating system running itsdiagnostic tests to evaluate the error event. The process then passes toblock 608 which illustrates the operating system generating an event logentry which includes the event data arranged in the standardized format.

[0051] Next, block 610 depicts the operating system forwarding the eventlog entry to the service program. Block 612, then, illustrates theservice program determining whether an event log entry has already beenlogged for this particular error event. If an event log entry hasalready been logged, a counter is incremented to indicate the number oftimes an error log entry is received for this particular error event. Ifno error event log entry has already been logged, this event log entrywill be logged. The process then terminates as depicted by block 614.

[0052] It is important to note that while the present invention has beendescribed in the context of a fully functioning data processing system,those of ordinary skill in the art will appreciate that the processes ofthe present invention are capable of being distributed in the form of acomputer readable medium of instructions and a variety of forms and thatthe present invention applies equally regardless of the particular typeof signal bearing media actually used to carry out the distribution.Examples of computer readable media include recordable-type media, suchas a floppy disk, a hard disk drive, a RAM, CD-ROMs, DVD-ROMs, andtransmission-type media, such as digital and analog communicationslinks, wired or wireless communications links using transmission forms,such as, for example, radio frequency and light wave transmissions. Thecomputer readable media may take the form of coded formats that aredecoded for actual use in a particular data processing system.

[0053] The description of the present invention has been presented forpurposes of illustration and description, and is not intended to beexhaustive or limited to the invention in the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art. The embodiment was chosen and described in order to bestexplain the principles of the invention, the practical application, andto enable others of ordinary skill in the art to understand theinvention for various embodiments with various modifications as aresuited to the particular use contemplated.

What is claimed is:
 1. A method in a computer system for reporting errorevents which occur within said computer system, said computer systemincluding a plurality of logical partitions, each of said plurality oflogical partitions including a different one of a plurality of operatingsystems, said method comprising the steps of: specifying a format forreporting error events; detecting an error event occurring within one ofsaid plurality of logical partitions; formatting information about saiderror event in said format, wherein said format is utilized by each ofsaid plurality of different operating systems to report error events. 2.The method according to claim 1, wherein said step of detecting an errorevent further comprises the step of detecting a hardware error event. 3.The method according to claim 1, further comprising the step ofspecifying an operating system identification field in said format foridentifying an operating system included within one of said plurality oflogical partitions within which said error event occurred.
 4. The methodaccording to claim 1, further comprising the step of specifying adiagnostic format field in said format for identifying a diagnosticformat used by an operating system included within one of said pluralityof logical partitions within which said error event occurred to analyzesaid error event.
 5. The method according to claim 1, further comprisingthe step of specifying an error code field in said format foridentifying an error code which describes said error event.
 6. Themethod according to claim 1, further comprising the step of specifying aunit identifier field in said format for identifying a unit within whichsaid error event occurred.
 7. The method according to claim 1, furthercomprising the step of specifying a machine type/model/serial numberfield in said format for identifying said computer system.
 8. The methodaccording to claim 1, further comprising the step of specifying an errortime-stamp field in said format for identifying a date and a time whensaid error event occurred.
 9. The method according to claim 1, furthercomprising the step of reporting said error event utilizing said format.10. The method according to claim 1, further comprising the step oflogging said error event in said computer system utilizing said format.11. The method according to claim 10, further comprising the step ofspecifying a log time-stamp field in said format for identifying a dateand a time when said error event was logged in said computer system. 12.A method for reporting service events which occur in one of a pluralityof different computer systems, said method comprising the steps of:specifying a format for reporting error information; detecting an errorevent occurring within one of said plurality of different computersystems, each of said plurality of different computer systems executingone of a plurality of different operating systems; formattinginformation about said error event in said format, wherein said formatis utilized by each of said plurality of different operating systems.13. The method according to claim 12, wherein said step of detecting anerror event further comprises the step of detecting a hardware errorevent.
 14. The method according to claim 12, further comprising the stepof specifying an operating system identification field in said formatfor identifying an operating system being executed by one of saidplurality of computer systems within which said error event occurred.15. The method according to claim 12, further comprising the step ofspecifying a diagnostic format field in said format for identifying adiagnostic format used by an operating system being executed by one ofsaid plurality of computer systems within which said error eventoccurred to analyze said error event.
 16. The method according to claim12, further comprising the step of specifying an error code field insaid format for identifying an error code which describes said errorevent.
 17. The method according to claim 12, further comprising the stepof specifying a unit identifier field in said format for identifying aunit within which said error event occurred.
 18. The method according toclaim 12, further comprising the step of specifying a machinemodel/type/serial number field in said format for identifying said oneof said plurality of different computer systems within which said errorevent occurred.
 19. The method according to claim 12, further comprisingthe step of specifying an error time-stamp field in said format foridentifying a date and a time when said error event occurred.
 20. Themethod according to claim 12, further comprising the step of reportingsaid error event utilizing said format.
 21. The method according toclaim 12, further comprising the step of logging said error event insaid one of said plurality of computer systems utilizing said format.22. The method according to claim 21, further comprising the step ofspecifying a log time-stamp field in said format for identifying a dateand a time when said error event was logged within said one of saidplurality of computer systems.
 23. A computer program product in acomputer system for reporting error events which occur within saidcomputer system, said computer system including a plurality of logicalpartitions, each of said plurality of logical partitions including adifferent one of a plurality of operating systems, said productcomprising: instruction means for specifying a format for reportingerror events; instruction means for detecting an error event occurringwithin one of said plurality of logical partitions; instruction meansfor formatting information about said error event in said format,wherein said format is utilized by each of said plurality of differentoperating systems to report error events.
 24. The product according toclaim 23, wherein said instruction means for detecting an error eventfurther comprises instruction means for detecting a hardware errorevent.
 25. The product according to claim 23, further comprisinginstruction means for specifying an operating system identificationfield in said format for identifying an operating system included withinone of said plurality of logical partitions within which said errorevent occurred.
 26. The product according to claim 23, furthercomprising instruction means for specifying a diagnostic format field insaid format for identifying a diagnostic format used by an operatingsystem included within one of said plurality of logical partitionswithin which said error event occurred to analyze said error event. 27.The product according to claim 23, further comprising instruction meansfor specifying an error code field in said format for identifying anerror code which describes said error event.
 28. The product accordingto claim 23, further comprising instruction means for specifying a unitidentifier field in said format for identifying a unit within which saiderror event occurred.
 29. The product according to claim 23, furthercomprising instruction means for specifying a machine type/model/serialnumber field in said format for identifying said computer system. 30.The product according to claim 23, further comprising instruction meansfor specifying an error time-stamp field in said format for identifyinga date and a time when said error event occurred.
 31. The productaccording to claim 23, further comprising instruction means forreporting said error event utilizing said format.
 32. The productaccording to claim 23, further comprising instruction means for loggingsaid error event in said computer system utilizing said format.
 33. Theproduct according to claim 32, further comprising instruction means forspecifying a log time-stamp field in said format for identifying a dateand a time when said error event was logged in said computer system. 34.A computer system for reporting error events which occur within saidcomputer system, said computer system including a plurality of logicalpartitions, each of said plurality of logical partitions including adifferent one of a plurality of operating systems, comprising: a formatfor reporting error events; an error event occurring within one of saidplurality of logical partitions; and said computer system for formattinginformation about said error event in said format, wherein said formatis utilized by each of said plurality of different operating systems toreport error events.
 35. The system according to claim 34, furthercomprising said computer system for detecting a hardware error event.36. The system according to claim 34, further comprising operatingsystem identification field being specified in said format foridentifying an operating system included within one of said plurality oflogical partitions within which said error event occurred.
 37. Thesystem according to claim 34, further comprising a diagnostic formatfield being specified in said format for identifying a diagnostic formatused by an operating system included within one of said plurality oflogical partitions within which said error event occurred to analyzesaid error event.
 38. The system according to claim 34, furthercomprising an error code field being specified in said format foridentifying an error code which describes said error event.
 39. Thesystem according to claim 34, further comprising a unit identifier fieldbeing specified in said format for identifying a unit within which saiderror event occurred.
 40. The system according to claim 34, furthercomprising a machine type/model/serial number field being specified insaid format for identifying said computer system.
 41. The systemaccording to claim 34, further comprising an error time-stamp fieldbeing specified in said format for identifying a date and a time whensaid error event occurred.
 42. The system according to claim 34, furthercomprising means for reporting said error event utilizing said format.43. The system according to claim 34, further comprising said errorevent being logged in said computer system utilizing said format. 44.The system according to claim 43, further comprising a log time-stampfield being specified in said format for identifying a date and a timewhen said error event was logged in said computer system.